Skip to content

feat: add waitForInspectableTarget option (fix #145) - #191

Open
gamtiq wants to merge 1 commit into
GoogleChrome:mainfrom
gamtiq:waitForInspectableTarget
Open

feat: add waitForInspectableTarget option (fix #145)#191
gamtiq wants to merge 1 commit into
GoogleChrome:mainfrom
gamtiq:waitForInspectableTarget

Conversation

@gamtiq

@gamtiq gamtiq commented Mar 16, 2020

Copy link
Copy Markdown

I've added new option waitForInspectableTarget that allows to wait until target list is available. It should fix #145.

Comment thread README.md
// (optional) Interval in ms, which defines whether and how long an inspectable target should be awaited.
// `0` means that list of inspectable targets will not be requested and awaited.
// Default: 0
waitForInspectableTarget: number;

@connorjclark connorjclark Mar 14, 2022

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wondering if this ought to be the default behavior. about to do a major version anyhow, so we can do a breaking change. Will play with this more later.

also, having a timeout be configurable doesn't make much sense to a user (what is a "correct" value?), should probably just internally wait for some reasonable upper limit (10s?) then fail.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Occasional "No inspectable targets" error when launching chrome with a very short connectionPollInterval

2 participants